Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create catalog-info file #1406

Closed
wants to merge 4 commits into from
Closed

Conversation

elastic-backstage-prod[bot]
Copy link

If you already have a ./catalog-info.yaml file defined in your repository, you probably want to close this PR.

If not - this PR provides you with the scaffolding for one. The catalog-info.yaml file is where you can define your infrastructure needs (such as Buildkite pipelines) in the form of Real Resource Entities.


If you already have a Buildkite pipeline defined in the elastic/ci repository, you can copy its definition in this catalog-info.yaml file (see instructions).

Once the pipeline definition is ingested into Backstage, Terrazzo will emit a warning about a duplicate definition with a warning similar to:
🙈 Ignoring remote manifest in favour of local one: buildkite.elastic.dev/v1=>Pipeline=> your-pipeline

At this point, it is safe for you to delete the Pipeline definition from the elastic/ci repository.

Copy link

❌ Author of the following commits did not sign a Contributor Agreement:
259a6e9

Please, read and sign the above mentioned agreement if you want to contribute to this project

@esenmarti esenmarti requested a review from pquentin June 13, 2024 10:25
@esenmarti
Copy link
Contributor

Hi @pquentin . Could we submit this PR?

@pquentin
Copy link
Member

We can't due to the CLA check. I'll resubmit it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants